Providing Aggregate Playback Information

ABSTRACT

System, method, and apparatus including receiving an identification of content played by a playback system and an identification of location of the playback system. A playlist of content is associated with the location. A request is received to retrieve the playlist of content and the requested playlist of content is sent to a playback system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/728,144 entitled “Providing Aggregate PlaybackInformation” filed on Oct. 9, 2017, which is a continuation of U.S.patent application Ser. No. 14/862,048 entitled “Location-BasedPlaylist” filed on Sep. 22, 2015, which is a continuation of U.S. patentapplication Ser. No. 13/531,709 entitled “Collecting and Providing LocalPlayback System Information” filed on Jun. 25, 2012, each of which ishereby incorporated by reference in its entirety for all purposes.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer electronics and, moreparticularly, to collecting and providing access to aggregated playbackdata regarding content played via one or more devices on one or moreplayback data networks.

BACKGROUND

Technological advancements have increased the accessibility of musiccontent, as well as other types of media, such as television content,movies, and interactive content. For example, a user can access audio,video, or both audio and video content over the Internet through anonline store, an Internet radio station, a music service, a movieservice, and so on, in addition to the more traditional avenues ofaccessing audio and video content. Demand for audio, video, and bothaudio and video content inside and outside of the home continues toincrease.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologyare better understood with regard to the following description, appendedclaims, and accompanying drawings where:

FIG. 1 shows an illustration of an example system in which embodimentsof the methods and apparatus disclosed herein can be implemented;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and speakers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an example ad-hoc playback network;

FIG. 7 shows a system including a plurality of networks including acloud-based network and at least one local playback network;

FIG. 8 shows an illustration of an example system to aggregate and sharecontent usage and settings data from one or more local playbacknetworks.

FIG. 9 depicts an example heat map indicating a frequency of which aparticular genre of music was played by region.

FIG. 10 shows a flow diagram for an example method to aggregate contentdata from one or more local playback systems.

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the present disclosure is notlimited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

The presently described technology enables the collection and use ofinformation gathered from one or more networked audio playback systems.System level, content level, or both kinds of information, such asdescribed herein, may be intelligently gathered and collected from localplayback systems by one or more host or server devices via the cloud.The audio playback systems may be located in a specific geographicregion or span the entire globe. Further, an audio playback system mayinclude a system to be used as part of a permanent audio solution suchas in a home or office or other space, as a portable solution, as anin-vehicle audio system, or as any system where audio can be reproduced.

Data collected from the pool of audio playback systems may be used in avariety of applications. By way of illustration, the data may be founduseful by the users of the playback systems, manufacturers of theplayback system equipment, those in the music industry, contentproviders, and any other person or entity that may have an interest insuch information. In some embodiments, a playback system may beautomatically adjusted responsive to accessing such information. In someembodiments, the information may be used to facilitate a social aspectamongst listeners. In some embodiments, a manufacturer can use theinformation to design new products or reconfigure old ones. In someembodiments, the music industry can use the information to makebetter-informed strategy decisions. Many other uses of such informationand embodiments are described herein.

For instance, certain embodiments provide a method to collect andorganize data from an audio playback network. The example methodincludes collecting, using a processor, data relating to playback ofcontent at an audio playback network. The example method includesanalyzing the collected data based on at least one characteristic. Theexample method includes generating a representation of the analysis ofthe collected data. The example method includes providing therepresentation to the audio playback network.

In another instance, certain embodiments provide a computer readablestorage medium including instructions for execution by a processor, theinstructions, when executed, cause the processor to implement a methodto collect and organize data from a local playback network. The examplemethod includes collecting data relating to playback of content at alocal playback network. The example method includes analyzing thecollected data based on at least one characteristic. The example methodincludes generating a representation of the analysis of the collecteddata. The example method includes providing the representation to thelocal playback network.

In yet another instance, certain examples provide an apparatus includinga wireless communication interface to communicate with at least onelocal playback network. The example apparatus includes a memory to storedata and a processor. The example processor is arranged to collect datarelating to playback of content at a local playback network. The exampleprocessor is arranged to analyze the collected data based on at leastone characteristic. The example processor is arranged to generate arepresentation of the analysis of the collected data. The exampleprocessor is arranged to provide the representation to the localplayback network.

II. An Example Operating Environment

Referring now to the drawings, in which like numerals can refer to likeparts throughout the figures, FIG. 1 shows an example system 100 inwhich one or more embodiments disclosed herein can be practiced orimplemented.

By way of illustration, system 100 represents a home presentlyconfigured with multiple zones, though the home could have beenconfigured with only one zone. Each zone in the home, for example, mayrepresent a different room or space, such as an office, bathroom,bedroom, kitchen, dining room, family room, home theater room, utilityor laundry room, and patio. A single zone might also include multiplerooms if so configured. One or more of zone players 102-124 are shown ineach respective zone of the home. A zone player 102-124, also referredto as a playback device, multimedia unit, speaker, player, and so on,provides audio, video, and/or audiovisual output. Controller 130provides control to system 100. Controller 130 may be fixed to a zone,or alternatively, mobile such that it can be moved about the zones.System 100 may also include more than one controller 130. System 100illustrates an example whole house audio system, though it is understoodthat the technology described herein is not limited to its particularplace of application or to an expansive system like a whole house audiosystem 100 of FIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspondto any of the zone players 102-124 of FIG. 1, for example. In someembodiments, audio is reproduced using only a single zone player, suchas by a full-range player. In some embodiments, audio is reproducedusing two or more zone players, such as by using a combination offull-range players or a combination of full-range and specializedplayers. In some embodiments, zone players 200-204 may also be referredto as a “smart speaker,” because they contain processing capabilitiesbeyond the reproduction of audio, more of which is described below.

FIG. 2A illustrates zone player 200 that includes sound producingequipment 208 capable of reproducing full-range sound. The sound maycome from an audio signal that is received and processed by zone player200 over a wired or wireless data network. Sound producing equipment 208includes one or more built-in amplifiers and one or more speakers. Abuilt-in amplifier is described more below with respect to FIG. 4. Aspeaker or acoustic transducer can include, for example, any of atweeter, a mid-range driver, a low-range driver, and a subwoofer. Insome embodiments, zone player 200 can be statically or dynamicallyconfigured to play stereophonic audio, monaural audio, or both. In someembodiments, zone player 200 is configured to reproduce a subset offull-range sound, such as when zone player 200 is grouped with otherzone players to play stereophonic audio, monaural audio, and/or surroundaudio or when the audio content received by zone player 200 is less thanfull-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifierto power a set of detached speakers 210. A detached speaker can include,for example, any type of loudspeaker. Zone player 202 may be configuredto power one, two, or more separate loudspeakers. Zone player 202 may beconfigured to communicate an audio signal (e.g., right and left channelaudio or more channels depending on its configuration) to the detachedspeakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-inamplifier, but is configured to communicate an audio signal, receivedover a data network, to an audio (or “audio/video”) receiver 214 withbuilt-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of thezone players 102 to 124 can retrieve audio directly from a source. Forexample, a zone player may contain a playlist or queue of audio items tobe played. Each item in the queue may comprise a uniform resourceidentifier (URI) or some other identifier. The URI or identifier canpoint the zone player to the audio source. The source might be found onthe Internet (e.g., the cloud), locally from another device over datanetwork 128, the controller 130, stored on the zone player itself, orfrom an audio source communicating directly to the zone player. In someembodiments, the zone player can reproduce the audio itself, send it toanother zone player for reproduction, or both where the audio is playedby the zone player and one or more additional zone players in synchrony.In some embodiments, the zone player can play a first audio content (ornot play at all), while sending a second, different audio content toanother zone player(s) for reproduction.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presentlyoffers for sale zone players referred to as a “PLAY:5,” “PLAY:3,”“CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/orfuture zone players can additionally or alternatively be used toimplement the zone players of example embodiments disclosed herein.Additionally, it is understood that a zone player is not limited to theparticular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOSproduct offerings. For example, a zone player may include a wired orwireless headphone. In yet another example, a zone player might includea sound bar for television. In yet another example, a zone player caninclude or interact with a docking station for an Apple IPOD™ or similardevice.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station302. By way of illustration, controller 300 can correspond tocontrolling device 130 of FIG. 1. Docking station 302, if provided, maybe used to charge a battery of controller 300. In some embodiments,controller 300 is provided with a touch screen 304 that allows a user tointeract through touch with the controller 300, for example, to retrieveand navigate a playlist of audio items, control operations of one ormore zone players, and provide overall control of the systemconfiguration 100. In certain embodiments, any number of controllers canbe used to control the system configuration 100. In some embodiments,there can be a limit set on the number of controllers that can controlthe system configuration 100. The controllers might be wireless likewireless controller 300 or wired to data network 128.

In some embodiments, if more than one controller is used in system 100,then each controller may be coordinated to display common content, andmay all be dynamically updated to indicate changes made from a singlecontroller. Coordination can occur, for instance, by a controllerperiodically requesting a state variable directly or indirectly from oneor more zone players; the state variable may provide information aboutsystem 100, such as current zone group configuration, what is playing inone or more zones, volume levels, and other items of interest. The statevariable may be passed around on data network 128 between zone players(and controllers, if so desired) as needed or as often as programmed.

In addition, an application running on any network-enabled portabledevice, such as an IPHONE™ IPAD™ ANDROID™ powered phone, or any othersmart phone or network-enabled device can be used as controller 130. Anapplication running on a laptop or desktop personal computer (PC) orMac™ can also be used as controller 130. Such controllers may connect tosystem 100 through an interface with data network 128, a zone player, awireless router, or using some other configured connection path. Examplecontrollers offered by SONOS, Inc. of Santa Barbara, Calif. include a“Controller 200,” “SONOS CONTROL,” “SONOS® Controller for IPHONE,”“SONOS® Controller for IPHONE,” “SONOS® Controller for ANDROID, “SONOS®Controller for MAC or PC.”

c. Example Data Connection

Zone players 102 to 124 of FIG. 1 are coupled directly or indirectly toa data network, such as data network 128. Controller 130 may also becoupled directly or indirectly to data network 128 or individual zoneplayers. Data network 128 is represented by an octagon in the figure tostand out from other representative components. While data network 128is shown in a single location, it is understood that such a network isdistributed in and around system 100. Particularly, data network 128 canbe a wired network, a wireless network, or a combination of both wiredand wireless networks. In some embodiments, one or more of the zoneplayers 102-124 are wirelessly coupled to data network 128 based on aproprietary mesh network. In some embodiments, one or more of the zoneplayers 102-124 are wirelessly coupled to data network 128 using anon-mesh topology. In some embodiments, one or more of the zone players102-124 are coupled via a wire to data network 128 using Ethernet orsimilar technology. In addition to the one or more zone players 102-124connecting to data network 128, data network 128 can further allowaccess to a wide area network, such as the Internet.

In some embodiments, connecting any of the zone players 102-124, or someother connecting device, to a broadband router, can create data network128. Other zone players 102-124 can then be added wired or wirelessly tothe data network 128. For example, a zone player (e.g., any of zoneplayers 102-124) can be added to the system configuration 100 by simplypressing a button on the zone player itself (or perform some otheraction), which enables a connection to be made to data network 128. Thebroadband router can be connected to an Internet Service Provider (ISP),for example. The broadband router can be used to form another datanetwork within the system configuration 100, which can be used in otherapplications (e.g., web surfing). Data network 128 can also be used inother applications, if so programmed. An example, second network mayimplement SonosNet protocol, developed by SONOS, Inc. of Santa Barbara.SonosNet represents a secure, AES-encrypted, peer-to-peer wireless meshnetwork. Alternatively, in certain embodiments, the data network 128 isthe same network, such as a traditional wired or wireless network, usedfor other applications in the household.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, thefamily room of FIG. 1 contains two zone players 106 and 108, while thekitchen is shown with one zone player 102. In another example, the hometheater room contains additional zone players to play audio from a 5.1channel or greater audio source (e.g., a movie encoded with 5.1 orgreater audio channels). In some embodiments, one can position a zoneplayer in a room or space and assign the zone player to a new orexisting zone via controller 130. As such, zones may be created,combined with another zone, removed, and given a specific name (e.g.,“Kitchen”), if so desired and programmed to do so with controller 130.Moreover, in some embodiments, zone configurations may be dynamicallychanged even after being configured using controller 130 or some othermechanism.

In some embodiments, if a zone contains two or more zone players, suchas the two zone players 106 and 108 in the family room, then the twozone players 106 and 108 can be configured to play the same audio sourcein synchrony, or the two zone players 106 and 108 can be paired to playtwo separate sounds in left and right channels, for example. In otherwords, the stereo effects of a sound can be reproduced or enhancedthrough the two zone players 106 and 108, one for the left sound and theother for the right sound. In certain embodiments, paired zone players(also referred to as “bonded zone players”) can play audio in synchronywith other zone players in the same or different zones.

In some embodiments, two or more zone players can be sonicallyconsolidated to form a single, consolidated zone player. A consolidatedzone player (though made up of multiple, separate devices) can beconfigured to process and reproduce sound differently than anunconsolidated zone player or zone players that are paired, because aconsolidated zone player will have additional speaker drivers from whichsound can be passed. The consolidated zone player can further be pairedwith a single zone player or yet another consolidated zone player. Eachplayback device of a consolidated playback device can be set in aconsolidated mode, for example.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing controller 130, and not by physically connecting and re-connectingspeaker wire, for example, to individual, discrete speakers to createdifferent configurations. As such, certain embodiments described hereinprovide a more flexible and dynamic platform through which soundreproduction can be offered to the end-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. Synchronizing playback amongst zones allows forsomeone to pass through zones while seamlessly (or substantiallyseamlessly) listening to the audio. Further, zones can be put into a“party mode” such that all associated zones will play audio insynchrony.

Sources of audio content to be played by zone players 102-124 arenumerous. In some embodiments, music on a zone player itself may beaccessed and a played. In some embodiments, music from a personallibrary stored on a computer or networked-attached storage (NAS) may beaccessed via the data network 128 and played. In some embodiments,Internet radio stations, shows, and podcasts can be accessed via thedata network 128. Music or cloud services that let a user stream and/ordownload music and audio content can be accessed via the data network128. Further, music can be obtained from traditional sources, such as aturntable or CD player, via a line-in connection to a zone player, forexample. Audio content can also be accessed using a different protocol,such as AIRPLAY™, which is a wireless technology by Apple, Inc., forexample. Audio content received from one or more sources can be sharedamongst the zone players 102 to 124 via data network 128 and/orcontroller 130. The above-disclosed sources of audio content arereferred to herein as network-based audio information sources. However,network-based audio information sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120are coupled to an audio information source such as a television 132. Insome examples, the television 132 is used as a source of audio for thehome theater zone players 116, 118, 120, while in other examples audioinformation from the television 132 can be shared with any of the zoneplayers 102-124 in the audio system 100.

III. Zone Players

Referring now to FIG. 4, there is shown an example block diagram of azone player 400 in accordance with an embodiment. Zone player 400includes a network interface 402, a processor 408, a memory 410, anaudio processing component 412, one or more modules 414, an audioamplifier 416, and a speaker unit 418 coupled to the audio amplifier416. FIG. 2A shows an example illustration of such a zone player. Othertypes of zone players may not include the speaker unit 418 (e.g., suchas shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player 400 can beintegrated into another component. For example, the zone player 400could be constructed as part of a television, lighting, or some otherdevice for indoor or outdoor use.

In some embodiments, network interface 402 facilitates a data flowbetween zone player 400 and other devices on a data network 128. In someembodiments, in addition to getting audio from another zone player ordevice on data network 128, zone player 400 may access audio directlyfrom the audio source, such as over a wide area network or on the localnetwork. In some embodiments, the network interface 402 can furtherhandle the address part of each packet so that it gets to the rightdestination or intercepts packets destined for the zone player 400.Accordingly, in certain embodiments, each of the packets includes anInternet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, network interface 402 can include one or both of awireless interface 404 and a wired interface 406. The wireless interface404, also referred to as a radio frequency (RF) interface, providesnetwork interface functions for the zone player 400 to wirelesslycommunicate with other devices (e.g., other zone player(s), speaker(s),receiver(s), component(s) associated with the data network 128, and soon) in accordance with a communication protocol (e.g., any wirelessstandard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, or 802.15).Wireless interface 404 may include one or more radios. To receivewireless signals and to provide the wireless signals to the wirelessinterface 404 and to transmit wireless signals, the zone player 400includes one or more antennas 420. The wired interface 406 providesnetwork interface functions for the zone player 400 to communicate overa wire with other devices in accordance with a communication protocol(e.g., IEEE 802.3). In some embodiments, a zone player includes both ofthe interfaces 404 and 406. In some embodiments, a zone player 400includes only the wireless interface 404 or the wired interface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatcan be loaded with one or more software module(s) 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine-readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network (e.g.,using a uniform resource locator (URL) or some other identifier). Insome embodiments, a task may be for the zone player 400 to send audiodata to another zone player or device on a network. In some embodiments,a task may be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmay be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks can be achieved via the one or more software module(s) 414 and theprocessor 408.

The audio processing component 412 can include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Insome embodiments, the audio processing component 412 may be part ofprocessor 408. In some embodiments, the audio that is retrieved via thenetwork interface 402 is processed and/or intentionally altered by theaudio processing component 412. Further, the audio processing component412 can produce analog audio signals. The processed analog audio signalsare then provided to the audio amplifier 416 for play back throughspeakers 418. In addition, the audio processing component 412 caninclude circuitry to process analog or digital signals as inputs to playfrom zone player 400, send to another zone player on a network, or bothplay and send to another zone player on the network. An example inputincludes a line-in connection (e.g., an auto-detecting 3.5 mm audioline-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418can include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver can be a subwoofer (e.g., for low frequencies), amid-range driver (e.g., middle frequencies), and a tweeter (e.g., highfrequencies), for example. An enclosure can be sealed or ported, forexample. Each transducer may be driven by its own individual amplifier.

A commercial example, presently known as the PLAY:5, is a zone playerwith a built-in amplifier and speakers that is capable of retrievingaudio directly from the source, such as on the Internet or on the localnetwork, for example. In particular, the PLAY:5 is a five-amp,five-driver speaker system that includes two tweeters, two mid-rangedrivers, and one woofer. When playing audio content via the PLAY:5, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies, but from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon, can be played from the PLAY:5.

IV. Controller

Referring now to FIG. 5, there is shown an example block diagram forcontroller 500, which can correspond to the controlling device 130 inFIG. 1. Controller 500 can be used to facilitate the control ofmulti-media applications, automation and others in a system. Inparticular, the controller 500 may be configured to facilitate aselection of a plurality of audio sources available on the network andenable control of one or more zone players (e.g., the zone players102-124 in FIG. 1) through a wireless or wired network interface 508.According to one embodiment, the wireless communications is based on anindustry standard (e.g., infrared, radio, wireless standards includingIEEE 802.11a, 802.11b 802.11g, 802.11n, or 802.15, and so on). Further,when a particular audio is being accessed via the controller 500 orbeing played via a zone player, a picture (e.g., album art) or any otherdata, associated with the audio and/or audio source can be transmittedfrom a zone player or other electronic device to controller 500 fordisplay.

Controller 500 is provided with a screen 502 and an input interface 514that allows a user to interact with the controller 500, for example, tonavigate a playlist of many multimedia items and to control operationsof one or more zone players. The screen 502 on the controller 500 can bean LCD screen, for example. The screen 500 communicates with and iscommanded by a screen driver 504 that is controlled by a microcontroller(e.g., a processor) 506. The memory 510 can be loaded with one or moreapplication modules 512 that can be executed by the microcontroller 506with or without a user input via the user interface 514 to achievecertain tasks. In some embodiments, an application module 512 isconfigured to facilitate grouping a number of selected zone players intoa zone group and synchronizing the zone players for audio play back. Insome embodiments, an application module 512 is configured to control theaudio sounds (e.g., volume) of the zone players in a zone group. Inoperation, when the microcontroller 506 executes one or more of theapplication modules 512, the screen driver 504 generates control signalsto drive the screen 502 to display an application specific userinterface accordingly.

The controller 500 includes a network interface 508 that facilitateswired or wireless communication with a zone player. In some embodiments,the commands such as volume control and audio playback synchronizationare sent via the network interface 508. In some embodiments, a savedzone group configuration is transmitted between a zone player and acontroller via the network interface 508. The controller 500 can controlone or more zone players, such as 102-124 of FIG. 1. There can be morethan one controller for a particular system, and each controller mayshare common information with another controller, or retrieve the commoninformation from a zone player, if such a zone player storesconfiguration data (e.g., such as a state variable). Further, acontroller can be integrated into a zone player.

It should be noted that other network-enabled devices such as anIPHONE®, IPAD® or any other smart phone or network-enabled device (e.g.,a networked computer such as a PC or Mac®) can also be used as acontroller to interact or control zone players in a particularenvironment. In some embodiments, a software application or upgrade canbe downloaded onto a network-enabled device to perform the functionsdescribed herein.

In certain embodiments, a user can create a zone group (also referred toas a bonded zone) including at least two zone players from thecontroller 500. The zone players in the zone group can play audio in asynchronized fashion, such that all of the zone players in the zonegroup play back an identical audio source or a list of identical audiosources in a synchronized manner such that no (or substantially no)audible delays or hiccups are to be heard. Similarly, in someembodiments, when a user increases the audio volume of the group fromthe controller 500, the signals or data of increasing the audio volumefor the group are sent to one of the zone players and causes other zoneplayers in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplay back is to link a number of zone players together to form a group.To link a number of zone players together, a user can manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of the six zoneplayers, for example, by starting with a single zone and then manuallylinking each zone to that zone.

In certain embodiments, a set of zones can be dynamically linkedtogether using a command to create a zone scene or theme (subsequent tofirst creating the zone scene). For instance, a “Morning” zone scenecommand can link the Bedroom, Office, and Kitchen zones together in oneaction. Without this single command, the user would need to manually andindividually link each zone. The single command may include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed action. Other kinds of zone scenes can be programmed.

In certain embodiments, a zone scene can be triggered based on time(e.g., an alarm clock function). For instance, a zone scene can be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration. Although any particular zone can be triggered to an“On” or “Off” state based on time, for example, a zone scene enables anyzone(s) linked to the scene to play a predefined audio (e.g., afavorable song, a predefined playlist) at a specific time and/or for aspecific duration. If, for any reason, the scheduled music failed to beplayed (e.g., an empty playlist, no connection to a share, failedUniversal Plug and Play (UPnP), no Internet connection for an InternetRadio station, and so on), a backup buzzer can be programmed to sound.The buzzer can include a sound file that is stored in a zone player, forexample.

V. Example Ad-Hoc Network

Examples will now be provided to describe, for purposes of illustration,certain base systems and methods to provide and facilitate connection toa playback network according to an embodiment. FIG. 6 shows that thereare three zone players 602, 604 and 606 and a controller 608 that form anetwork branch that is also referred to as an Ad-Hoc network 610. Thenetwork 610 may be wireless, wired, or a combination of wired andwireless. In general, an Ad-Hoc (or “spontaneous”) network is a localarea network or other small network in which there is no one accesspoint for all traffic. With an established Ad-Hoc network 610, thedevices 602, 604, 606 and 608 can all communicate with each other in a“peer-to-peer” style of communication, for example. Furthermore, devicesmay come/and go from the network 610, and the network 610 willautomatically reconfigure itself without needing the user to reconfigurethe network 610. While an Ad-Hoc network is referenced in FIG. 6, it isunderstood that a playback network may be based on a type of networkthat is completely or partially different from an Ad-Hoc network.

Using the Ad-Hoc network 610, the devices 602, 604, 606, and 608 canshare or exchange one or more audio sources and be grouped to play thesame or different audio sources. For example, the devices 602 and 604are grouped to playback one piece of music, and at the same time, thedevice 606 plays back another piece of music. In other words, thedevices 602, 604, 606 and 608, as shown in FIG. 6, form a HOUSEHOLD thatdistributes audio and/or reproduces sound. As used herein, the termHOUSEHOLD (provided in uppercase letters to disambiguate from the user'sdomicile) is used to represent a collection of networked devices thatare cooperating to provide an application or service. An instance of aHOUSEHOLD is identified with a household ID 610 (or householdidentifier), though a HOUSEHOLD may be identified with a different areaor place.

In certain embodiments, a household identifier (HHID) is a short stringor an identifier that is computer-generated to help ensure that it isunique. Accordingly, the network 610 can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), SSID (a sequence ofalphanumeric characters as a name of a wireless network), and WEP keys(wired equivalent privacy or other security keys). In certainembodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of networknodes: a control point (CP) and a zone player (ZP). The control pointcontrols an overall network setup process and sequencing, including anautomatic generation of required network parameters (e.g., WEP keys). Inan embodiment, the CP also provides the user with a HOUSEHOLDconfiguration user interface. The CP function can be provided by acomputer running a CP application module, or by a handheld controller(e.g., the controller 508) also running a CP application module, forexample. The zone player is any other device on the network that isplaced to participate in the automatic configuration process. The ZP, asa notation used herein, includes the controller 508 or a computingdevice, for example. In some embodiments, the functionality, or certainparts of the functionality, in both the CP and the ZP are combined at asingle node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multipleCPs and ZPs that rendezvous and establish a known configuration suchthat they can use a standard networking protocol (e.g., IP over Wired orWireless Ethernet) for communication. In an embodiment, two types ofnetworks/protocols are employed: Ethernet 802.3 and Wireless 802.11g.Interconnections between a CP and a ZP can use either of thenetworks/protocols. A device in the system as a member of a HOUSEHOLDcan connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that atleast one device in a system is connected to both as a bridging device,thus providing bridging services between wired/wireless networks forothers. The zone player 606 in FIG. 6 is shown to be connected to bothnetworks, for example. The connectivity to the network 612 is based onEthernet and/or Wireless, while the connectivity to other devices 602,604 and 608 is based on Wireless and Ethernet if desired.

It is understood, however, that in some embodiments each zone player606, 604, 602 may access the Internet when retrieving media from thecloud (e.g., Internet) via the bridging device. For example, zone player602 may contain a uniform resource locator (URL) that specifies anaddress to a particular audio track in the cloud. Using the URL, thezone player 602 may retrieve the audio track from the cloud, andultimately play the audio out of one or more zone players.

VI. Example System Configuration

FIG. 7 shows a system including a plurality of networks including acloud-based network and at least one local playback network (i.e., atleast one audio playback network). The playback network includes aplurality of playback devices or players, though it is understood thatthe playback network may contain only one playback device. In certainembodiments, each player has an ability to retrieve its content forplayback. Control and content retrieval can be distributed orcentralized, for example. Input can include streaming content providerinput, third party application input, mobile device input, user input,and/or other playback network input into the cloud for localdistribution and playback.

As illustrated by the example system 700 of FIG. 7, a plurality ofcontent providers 720-750 can be connected to one or more local playbacknetworks 760-770 via a cloud and/or other network 710. Using the cloud710, a remote host or server 720 (e.g., Sonos™), a mobile device 730, athird party application 740, a content provide 750 and so on can providemultimedia content (requested or otherwise) to local playback networks760, 770. Within each local playback network 760, 770, a controller 762,772 and a playback device 764, 774 can be used to playback audiocontent.

VII. Collected Data and Access to Collected Data

In an example system such as the one shown in FIG. 1, 6 or 7, where aSONOS system, for example, including one or more playback devices andone or more controllers is connected together in a local area network(LAN), the ability to capture information about the system configurationand/or the audio that is played via the system, including items like theaudio source, the zone and/or zone player in which audio is played, thegenre of music, the equalization, the volume levels, the time of day theaudio is played, and where the playback system is geographically locatedmay be valuable. Further, the ability to cross-link these items, andothers, for example, linking the genre of music played to theequalization parameters or volume levels or zones or time-of-day, may bevaluable.

As described above, an embodiment includes collecting information aboutan audio playback system and transmitting information to a remote hostor server such that the information may be provided to and used byinterested persons or systems at a remote location. In anotherembodiment, obtaining data from a large number of local playback systemsor pool of playback systems provides an opportunity to look for patternsand respond effectively depending on the strategy. In yet anotherembodiment, information from the large data pool may be used to makesystem adjustments to even a single, local playback system. In yetanother embodiment, information from the large data pool may lead torecommendations to users of the playback systems.

In certain embodiments, approval must be granted by a user to gatherinformation from that user's local playback network. The approval may begiven via a configuration setting or option via a controller or via someother mechanism.

A. Information Data Collection

In an example system, audio and/or system configuration information, forexample, is collected about the local playback system. In someembodiments, the information is initially collected by a single deviceor a collection of devices in the local playback system. For example, asingle device may be determined (e.g., selected by configuration orpredetermined) to be responsible to collect information for the system,including information specific to players, zones, and/or zone groupsdifferent from the device. For information that is not already exchangedin the system or known by the responsible device, a message exchange orother information gathering technique, for example, can be used betweenthe responsible device and other devices in the local system to collectthe information. In another example, each device collects informationspecific to the players, zones, and/or zone groups of the device. In yetanother example, a subset of system devices (e.g., players but notcontrollers) collect system information including information bothspecific to the devices and from different devices. Information may bepassed between devices wirelessly or wired, or both using the samenetwork used to carry the audio content or a different network.

In an embodiment, the information collected from a playback system istransferred to a remote “cloud server” such as the Sonos cloud server720 in FIG. 7 where it can be stored, processed and/or made available toother interested persons or systems and devices. In some embodiments,the remote server represents a single server device or a collection ofservers such as a server farm. In certain embodiments, the informationis “pushed” from the responsible device(s) of the example system to theremote server. For example, based on a trigger or event, the examplesystem may transmit information data to the remote server. In otherembodiments, the information is “pulled” from the responsible device(s)of the example system by the server. For example, the remote server mayquery the example system for the information on a periodic basis orbased on an event.

In an embodiment, the information is transferred to the remote serverperiodically, and may be initiated by either the local system or theremote server. For example, the data may be transferred daily, weekly,or monthly from the local system to the remote server based on a timeclock and a periodicity (e.g., using a time clock and period maintainedon a device in the local system or on a remote server). When the timeperiod expires, the information is transferred to the server from theone or more responsible devices. In another embodiment, the data istransferred to the remote system based on certain, fixed time-periodssuch as the duration of a pilot or beta program of an associated device.The time period expiration may be determined, for example, by using atime clock maintained on a device in the local system or on a remoteserver. For example, at the end of a such a program, the data collectedover the time period of the program is transferred from the one or moreresponsible devices to the remote server. In yet another embodiment, thedata is transferred based on an event or a collection of events suchthat the number of such events cross a threshold. For example, theinformation data may be transferred to the remote server before a deviceis upgraded or after 20 hours of audio have been played on the system.In another embodiment, the data is transferred to the remote server asit is collected.

The collected information may be provided to and used by interestedpersons. For instance, in some embodiments, the data is used bylisteners. As an illustration, a listener may use the information in asocial context or look to the information for discovery and audiorecommendations. The listeners may include listeners of a local playbacksystem like a SONOS system where, for example, the information can beaccessed via a controller, listeners of audio in general such as using amobile phone or web application, or both. In some embodiments, the datais used by those who enable the listening experience, such as, forexample, manufacturers of equipment of a local playback system (e.g.,SONOS™ or some other provider whose speaker and/or other playback deviceis the final component in a content playback cycle), the contentproviders (e.g., PANDORA™, SPOTIFY™, RHAPSODY™, and other contentproviders), and the audio industry (e.g., music labels, artists, movieindustry, and so on) to name several examples. In yet other embodiments,the data is used by local systems for auto configuration based on, forexample, similar systems with similar capabilities or settings. In somecircumstances, the collected information may represent the mostcomprehensive data collection pertaining to the system and/or audioplayed via the system because the playback system is an audio sourceaggregator among other things.

B. Audio and Configuration Information

In certain embodiments, a local playback system may obtain audio contentfrom a large number of sources such as Internet services, cloudservices, stored media (e.g., audio or video stored locally or using acloud-based storage service), and so on, and play that content (e.g.,audio, video, etc.) via one or more playback devices. For example, alistener in a household might be listening to a specific Bill Evans jazzalbum in the living room that is streaming from an Internet on-demandservice, while another listener in the same household is listening topublic radio in the kitchen, while yet another listener in the samehousehold is listening to the new Radiohead album that is stored ontheir MAC™ device on the local network.

According to this example, as a result of the aggregation of sources bya single system, one or more devices of the playback system can obtaininformation regarding the content played back via the system. In someembodiments, the playback system can gather more knowledge about what,when and how content is being played than any other content provider orservice because only the local playback system knows what is currentlyplaying from all aggregated sources. In contrast, a specific contentprovider (e.g., SPOTIFY™) is not able to determine whether a locallystored content or content from another provider (e.g., RHAPSODY™) wasactually played. Also, information about some content may not be easilyidentifiable, such as information played from an Internet radio station(e.g., PANDORA™ and so on) where a streaming radio signal is providedinstead of song tracks or ID. In this instance, the local playbacknetwork can identify and aggregate what song(s) and/or other content arebeing played regardless of whether it's from Internet radio, localstorage, or selected on-demand. For instance, if the 80's hits are beingplayed from an Internet radio channel, the playback system may identifyindividual songs being played. Furthermore, the local system canaggregate the information from across multiple sources to determine, forexample, service-independent information related to a song, playbacksystem, and/or cross-linked song/system combination. For example, howoften the genre/artist/etc. is played in a household, what time thecontent is played, what volume level is selected for each genre, whatzone(s) are the content played in, what are the equalization (EQ)settings for the system, user, and/or content, what are the calibrationsettings for the system, what are the configuration settings, speakerarrangement, and so on. Statistic generation, data mining, and/or otherintelligence can be derived from the aggregated data, for example.

In certain embodiments, a cloud-based server like 720 in FIG. 7, forexample, may further gather and aggregate audio and system configurationinformation from multiple local playback systems. The combined, gatheredinformation can be combined, processed, and stored over one or moredatabases such that the information can be retrieved and used by a localplayback system, content provider, system provider, etc., to assist insystem configuration and to understand playback habits, listenerdemographics, content recommendations, development suggestions, otheruser feedback, and so on. This gathered information, derived from thesystem hardware/software on a local network, is in many cases morecomprehensive than that data collected by a single content provider oreven a group of content providers.

In one example embodiment, a graphical representation such as a heatmap, fractal map, tree map, choropleth map, etc., may be generated andused to show a user of a particular playback network what global orother network of users is playing. For example, a heat map displayed ona controller, such as described above, or on a web-site can show a userwhat songs/genres are “hot” right now or even over a time duration(e.g., over the last week, month, year, and so on). A graphicalrepresentation can categorize content based on musical attributes orfocus traits, such as rhythm, tonality, vocal harmonies, and so on.Graphical representations can be based on an entire network of users ora subset of users (e.g., a subset of users might register to a “jazz”group, and content from that group is aggregated and shared), forexample. Information can be conveyed to music industry and/or artists tohelp supply an appetite or interest in certain types of music, forexample. Additionally, playlists and/or other content from a large groupcan be aggregated, filtered, and shared, for example.

In another example embodiment, global settings such as EQ and/or otherconfiguration settings, can also be pulled from global users or a subsetof global users. Instead of relying on default settings configured on adevice by the factory that manufactured it, users can choose an EQsetting and/or other setting based on a large population of users. Forexample, one or more users may choose to share EQ and/or other settings.For example, settings can be taken from a whole set of users or friendsand/or other subsets can form shared settings groups or pools (e.g., afriend can share her EQ settings with other members of her friend'sgroup). By way of illustration, a controller might give a user theoption to view how others configured their EQ in similar settings or acontroller might suggest alternate default settings for a user or asystem based on settings from similar systems in the large population.In addition to viewing other configurations, a user may then select oneof the configurations for their system.

In yet another example, volume levels, time played, zones played,determination if an entire song is played, and so on may also be usefulto the certain people. For example, the music industry may learn andunderstand more about their audience by analyzing such data. Moreover,Internet radio stations may use the data to adapt their playlists basedon such information. By way of illustration, data collected mightinclude something like 35% of the users listen to jazz between the hoursof 5 PM and 6:30 PM and play the music at reduced volume levels from theaverage volume setting.

FIG. 8 illustrates an example system 800 to aggregate and share contentusage and settings information data from one or more local playbacknetworks. The example system 800 includes a plurality of local playbacksystems 810-812 connected via a communication network 820, such as acloud-based network, to a data server 830. The server 830 collects datafrom the local playback systems 810-812 regarding content playback,settings, preferences, etc., and stores, mines, and analyzes thecollected data to determine trends, favorites, best practices, preferredsettings, recommended/popular content, and so on. The server 830 canthen provide information back to one or more local playback systems810-812 via the network 820. The server 830 might represent a singleserver device, a server farm or a collection of servers.

In some embodiments, information from server 830 may be retrieved bydevices on individual playback networks and displayed to users oncontrollers of those systems. Data requests may be on-demand or madeperiodically. Zone players and/or controllers may perform the request.If a particular zone player requests the data, then the data ispreferably retrieved and shared with a controller. The data may be inthe form of raw data or assembled in some manner (e.g., a heat map ortable) before it is passed to the local playback system. If the data israw in form, then a zone player and/or controller may process the datato output a useable result to the user. Data may be further processedvia application software residing on a controller on the playbacknetwork. The application software may be third party developed.

FIG. 9 depicts an example heat map 900 indicating a frequency 910 ofwhich a particular genre 920 of music was played by region 930. Playbackfrequency 910 for music of a certain genre 920 (e.g., rock, pop,country, classical, top 40, etc.) can be collected from one or moreparticipating playback systems, aggregated and displayed via the heatmap 900. Playback frequency data 910 can be further categorized byregion 930 of monitoring, for example. Heat maps or other kinds ofvisual displays may be used to convey information to listeners and/orother persons interested in such data.

FIG. 10 shows a flow diagram for an example method 1000 to aggregatecontent data from one or more local playback systems. At block 1010,content being played back (or other configuration data) is identified ata local playback system. For example, a song being played through aSONOS™ speaker system is identified by the SONOS™ system. The song maybe played in an identified zone or zone group. The source of the songmay be identified. EQ and other configuration parameters, such asvolume, may be identified. For instance, a system might identify that at“5:37 PM,” Household 45689 is streaming and playing “Adagio” by “PepeRomero” from the album “The Art of Pepe Romero” from “Spotify” and isplaying in the “Kitchen Zone” at a current volume level of “5 out of10.” The system may record the information at programmed times,intervals, when an action or change occurs (e.g., new track plays or avolume change is detected) to the system, or at some other determinedtime. In some embodiments, the information may be collected locally andsent to a server in the cloud periodically or at other times. In someembodiments, the information is sent to a server in the cloud whenconvenient.

At block 1020, played content and/or other local system data is gatheredat a remote system. For example, an indication of played content (e.g.,a song name or other identifier, movie title, artist, genre, type, etc.)is gathered from one or more local playback systems at a remote dataserver (e.g., transmitted over a network for storage on a cloud-baseddata server, and so on). In certain embodiments, approval must be givenby a user to gather information from that user's local playback network.For example, a user must agree to share data, participate in aninformation-gathering program, etc.

At block 1030, data is associated with one or more metrics. For example,gathered data can be associated with a frequency, volume, genre,equalizer settings, configuration settings, playback device arrangement,location of playback, etc. One or more aspects of block 1030 may occurbefore block 1010 so as to identify which information is to be gathered.Additionally, steps may be taken at block 1030 that filters and/orcross-links data. For instance, it may be determined that 73% of userschange EQ settings when changing the music to hip hop.

At block 1040, a representation of the information is generated inassociation with the one or more metrics. For example, a heat map,table, settings file, etc., can be generated to represent all or part ofthe gathered information for one or more parameters or metrics. Otherkinds of visual displays, textual displays, or a combination can be usedto convey the information. In some embodiments, the representation ofinformation is generated by a remote server or workstation device. Insome embodiments, the representation is generated by a local device,such as a controller or zone player or some other device.

At block 1050, the aggregated and associated information can be sharedwith one or more users. For example, in some embodiments, recommendedsettings, songs, configurations, and so on can be provided for relay ordownload to a user's local playback network. A popular song list for agiven genre can be transferred to a user's local system, for example.Equalizer settings popular for a particular genre can be transferred toa user's local system to be available for user installation and/or toautomatically configure the user's local playback system and/or network,for example.

At block 1060, the information can be stored for later use, furtheranalysis, reporting, and so on. Such information may be stored at aremote device, local playback devices, or a combination of the two.

While not necessary, at block 1070, a local playback system and/ornetwork can be adjusted based on the aggregated and associatedinformation. For example, a local playlist can be updated based onprovided popular songs. A local playback network's zone groupconfiguration can be adjusted based on monitored zone group data, forexample. A local playback system's equalizer settings can be adjusted,for example. A local playback system's content queue can be indexed orsearched based on a measured popular characteristic such as genre,artist, rhythm, tonality, harmony, instrument, and so on. In someembodiments, the adjustments occur automatically upon detection of theinformation by a device on a playback network.

VIII. Conclusion

Various inventions have been described in sufficient detail with acertain degree of particularity. It is understood to those skilled inthe art that the present disclosure of embodiments has been made by wayof examples only and that numerous changes in the arrangement andcombination of parts can be resorted without departing from the spiritand scope of the present disclosure as claimed. While the embodimentsdiscussed herein can appear to include some limitations as to thepresentation of the information units, in terms of the format andarrangement, the embodiments have applicability well beyond suchembodiment, which can be appreciated by those skilled in the art.Accordingly, the scope of the present disclosure is defined by theappended claims rather than the forgoing description of embodiments.

For example, a method to collect and organize data from a local playbacknetwork includes collecting, using a processor, data relating toplayback of content at a local playback network; analyzing the collecteddata based on at least one characteristic; generating a representationof the analysis of the collected data; and providing the representationto the local playback network.

In another example, the method just above, wherein the at least onecharacteristic includes at least one of a content name, content type,content artist, volume, playback zone, equalizer setting, andconfiguration setting.

In yet another example, a method further comprises determining at leastone of recommended content and recommended setting based on the analysisof the collected data.

In another example, a method further comprises remotely providing the atleast one of recommended content and recommended setting to the localplayback network.

In another example, a method further comprises automatically adjustingat least one of content for playback and a local playback setting basedon the at least one of recommended content and recommended settingprovided to the local playback network.

In yet another example, at least one of recommended content andrecommended setting is provided to a plurality of local playbacknetworks associated by a group.

In another example, a method further comprises storing the at least oneof recommended content and recommended setting in a cloud-based storagefor access by the local playback network.

In another example, an apparatus includes a wireless communicationinterface to communicate with at least one local playback network; amemory to store data; and a processor to: collect data relating toplayback of content at a local playback network; analyze the collecteddata based on at least one characteristic; generate a representation ofthe analysis of the collected data; and provide the representation tothe local playback network.

Although the above discloses example systems, methods, apparatus, andarticles of manufacture including, among other components, firmwareand/or software executed on hardware, it should be noted that suchsystems, methods, apparatus, and/or articles of manufacture are merelyillustrative and should not be considered as limiting. For example, itis contemplated that any or all of these firmware, hardware, and/orsoftware components could be embodied exclusively in hardware,exclusively in software, exclusively in firmware, or in any combinationof hardware, software, and/or firmware. Accordingly, while the abovedescribes example systems, methods, apparatus, and/or articles ofmanufacture, the examples provided are not the only way(s) to implementsuch systems, methods, apparatus, and/or articles of manufacture.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, and so on, storing the softwareand/or firmware.

Reference herein to “embodiment” means that a particular feature,structure, or characteristic described in connection with the embodimentcan be included in at least one example embodiment of the invention. Theappearances of this phrase in various places in the specification arenot necessarily all referring to the same embodiment, nor are separateor alternative embodiments mutually exclusive of other embodiments. Assuch, the embodiments described herein, explicitly and implicitlyunderstood by one skilled in the art, can be combined with otherembodiments.

Systems, methods, apparatus, and articles of manufacture to facilitategathering, aggregation and analysis of content playback and system datafrom one or more local playback networks. Certain embodiments facilitateanalysis and recommendation to one or more local playback systems basedon the aggregated and analyzed data.

1. A cloud-based computing device comprising: at least one processor;non-transitory computer-readable medium; and program instructions storedon the non-transitory computer-readable medium that are executable bythe at least one processor and thereby cause the playback device to beconfigured to: receive, from a first playback device in a first localmedia playback system, (1) first audio playback information and (2)first playback device configuration information corresponding to thefirst audio playback information; receive, from each of a plurality ofother playback devices in a respective plurality of other local mediaplayback systems, (1) respective audio playback information and (2)respective playback device configuration information corresponding tothe respective audio playback information; based on at least the (1)respective audio playback information and (2) the respective playbackdevice configuration information corresponding to the respective audioplayback information, determine updated playback device configurationinformation for the first playback device; and transmit the updatedplayback device configuration information to the first playback device.2. The cloud-based computing device of claim 1, further comprisingprogram instructions stored on the non-transitory computer-readablemedium that are executable by the at least one processor and therebycause the cloud-based computing device to be configured to: cause anindication of the updated playback device configuration information tobe displayed via a controller device of the first local media playbacksystem.
 3. The cloud-based computing device of claim 2, furthercomprising program instructions stored on the non-transitorycomputer-readable medium that are executable by the at least oneprocessor and thereby cause the cloud-based computing device to beconfigured to: after causing the indication of the updated playbackdevice configuration information to be displayed via the controllerdevice of the first local media playback system, receive, from thecontroller device, a command to implement the updated playback deviceconfiguration information on the first playback device.
 4. Thecloud-based computing device of claim 1, wherein the programinstructions that are executable by the at least one processor andthereby cause the cloud-based computing device to be configured totransmit the updated playback device configuration information to thefirst playback device comprise program instructions that are executableby the at least one processor and thereby cause the cloud-basedcomputing device to be configured to automatically transmit the updatedplayback device configuration information to the first playback deviceafter determining the updated playback device configuration information.5. The cloud-based computing device of claim 1, wherein the respectiveplayback device configuration information comprises respectiveequalization information for each of the plurality of other playbackdevices, and wherein the program instructions that are executable by theat least one processor and thereby cause the cloud-based computingdevice to be configured to determine updated playback deviceconfiguration information for the first playback device comprise programinstructions that are executable by the at least one processor andthereby cause the cloud-based computing device to be configured todetermine updated equalization information for the first playbackdevice.
 6. The cloud-based computing device of claim 1, wherein thefirst audio playback information comprises audio playback informationrelated to first audio content played by the first playback device andat least second audio content played by a second playback device of thefirst local media playback system, and wherein the program instructionsthat are executable by the at least one processor and thereby cause thecloud-based computing device to be configured to determine updatedplayback device configuration information for the first playback devicecomprise program instructions that are executable by the at least oneprocessor and thereby cause the cloud-based computing device to beconfigured to determine updated playback device configurationinformation for the first playback device and the second playbackdevice.
 7. The cloud-based computing device of claim 1, wherein a firstportion of the first audio playback information includes audio playbackinformation corresponding to a first content provider and a secondportion of the first audio playback information includes audio playbackinformation corresponding to a second content provider.
 8. Anon-transitory computer-readable medium, wherein the non-transitorycomputer-readable medium is provisioned with program instructions thatare executable by at least one processor such that a cloud-basedcomputing device is configured to: receive, from a first playback devicein a first local media playback system, (1) first audio playbackinformation and (2) first playback device configuration informationcorresponding to the first audio playback information; receive, fromeach of a plurality of other playback devices in a respective pluralityof other local media playback systems, (1) respective audio playbackinformation and (2) respective playback device configuration informationcorresponding to the respective audio playback information; based on atleast the (1) respective audio playback information and (2) therespective playback device configuration information corresponding tothe respective audio playback information, determine updated playbackdevice configuration information for the first playback device; andtransmit the updated playback device configuration information to thefirst playback device.
 9. The non-transitory computer-readable medium ofclaim 8, wherein the non-transitory computer-readable medium is alsoprovisioned with program instructions that are executable by the atleast one processor such that the cloud-based computing device isconfigured to: cause an indication of the updated playback deviceconfiguration information to be displayed via a controller device of thefirst local media playback system.
 10. The non-transitorycomputer-readable medium of claim 9, wherein the non-transitorycomputer-readable medium is also provisioned with program instructionsthat are executable by the at least one processor such that thecloud-based computing device is configured to: after causing theindication of the updated playback device configuration information tobe displayed via the controller device of the first local media playbacksystem, receive, from the controller device, a command to implement theupdated playback device configuration information on the first playbackdevice.
 11. The non-transitory computer-readable medium of claim 8,wherein the program instructions that are executable by at least oneprocessor such that the cloud-based computing device is configured totransmit the updated playback device configuration information to thefirst playback device comprise program instructions that are executableby at least one processor such that the cloud-based computing device isconfigured to automatically transmit the updated playback deviceconfiguration information to the first playback device after determiningthe updated playback device configuration information.
 12. Thenon-transitory computer-readable medium of claim 8, wherein therespective playback device configuration information comprisesrespective equalization information for each of the plurality of otherplayback devices, and wherein the program instructions that areexecutable by at least one processor such that the cloud-based computingdevice is configured to determine updated playback device configurationinformation for the first playback device comprise program instructionsthat are executable by at least one processor such that the cloud-basedcomputing device is configured to determine updated equalizationinformation for the first playback device.
 13. The non-transitorycomputer-readable medium of claim 8, wherein the first audio playbackinformation comprises audio playback information related to first audiocontent played by the first playback device and at least second audiocontent played by a second playback device of the first local mediaplayback system, and wherein the program instructions that areexecutable by at least one processor such that the cloud-based computingdevice is configured to determine updated playback device configurationinformation for the first playback device comprise program instructionsthat are executable by at least one processor such that the cloud-basedcomputing device is configured to determine updated playback deviceconfiguration information for the first playback device and the secondplayback device.
 14. The non-transitory computer-readable medium ofclaim 8, wherein a first portion of the first audio playback informationincludes audio playback information corresponding to a first contentprovider and a second portion of the first audio playback informationincludes audio playback information corresponding to a second contentprovider.
 15. A method carried out by a cloud-based computing device,the method comprising: receiving, from a first playback device in alocal media playback system, (1) audio information data and (2) playbackdevice configuration information corresponding to the audio informationdata; receiving, from each of a plurality of other playback devices in arespective plurality of other local media playback systems, (1)respective audio information data and (2) respective playback deviceconfiguration data corresponding to the respective audio informationdata; based on at least the (1) respective audio information data and(2) the respective playback device configuration data corresponding tothe respective audio information data, determining updated playbackdevice configuration data for the first playback device; andtransmitting an indication of the updated playback device configurationdata to the first playback device.
 16. The method of claim 15, furthercomprising: causing an indication of the updated playback deviceconfiguration information to be displayed via a controller device of thefirst local media playback system.
 17. The method of claim 16, furthercomprising: after causing the indication of the updated playback deviceconfiguration information to be displayed via the controller device ofthe first local media playback system, receiving, from the controllerdevice, a command to implement the updated playback device configurationinformation on the first playback device.
 18. The method of claim 15,wherein transmitting the updated playback device configurationinformation to the first playback device comprises automaticallytransmitting the updated playback device configuration information tothe first playback device after determining the updated playback deviceconfiguration information.
 19. The method of claim 15, wherein therespective playback device configuration information comprisesrespective equalization information for each of the plurality of otherplayback devices, and wherein determining updated playback deviceconfiguration information for the first playback device comprisesdetermining updated equalization information for the first playbackdevice.
 20. The method of claim 15, wherein the first audio playbackinformation comprises audio playback information related to first audiocontent played by the first playback device and at least second audiocontent played by a second playback device of the first local mediaplayback system, and wherein determining updated playback deviceconfiguration information for the first playback device comprisesdetermining updated playback device configuration information for thefirst playback device and the second playback device.